-
Notifications
You must be signed in to change notification settings - Fork 25.5k
Mention zero-window state in networking docs #124967
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Mention zero-window state in networking docs #124967
Conversation
Clarify that it is expected sometimes to see inter-node connections sending zero-window advertisements as part of the usual TCP backpressure mechanism.
Pinging @elastic/es-docs (Team:Docs) |
Pinging @elastic/es-distributed-coordination (Team:Distributed Coordination) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM makes sense, this has come up a lot in various ways :)
Clarify that it is expected sometimes to see inter-node connections sending zero-window advertisements as part of the usual TCP backpressure mechanism.
💔 Backport failed
You can use sqren/backport to manually backport by running |
Clarify that it is expected sometimes to see inter-node connections sending zero-window advertisements as part of the usual TCP backpressure mechanism. Backport of elastic#124967 to 8.x
Backport is #124969 |
Clarify that it is expected sometimes to see inter-node connections sending zero-window advertisements as part of the usual TCP backpressure mechanism. Backport of #124967 to 8.x
Clarify that it is expected sometimes to see inter-node connections sending zero-window advertisements as part of the usual TCP backpressure mechanism. Backport of elastic#124967 to 8.x
Clarify that it is expected sometimes to see inter-node connections sending zero-window advertisements as part of the usual TCP backpressure mechanism. Backport of elastic#124967 to 8.x
* main: (95 commits) Mute org.elasticsearch.datastreams.lifecycle.DataStreamLifecycleServiceIT testLifecycleAppliedToFailureStore elastic#124999 Merge template mappings properly during validation (elastic#124784) [Build] Rework internal build plugin plugin to work with Isolated Projects (elastic#123461) [Build] Require reason for usesDefaultDistribution (elastic#124707) Mute org.elasticsearch.packaging.test.DockerTests test011SecurityEnabledStatus elastic#124990 Mute org.elasticsearch.xpack.ilm.TimeSeriesDataStreamsIT testRolloverAction elastic#124987 Mute org.elasticsearch.packaging.test.BootstrapCheckTests test10Install elastic#124957 Mute org.elasticsearch.integration.DataStreamLifecycleServiceRuntimeSecurityIT testRolloverLifecycleAndForceMergeAuthorized elastic#124978 Mute org.elasticsearch.xpack.esql.action.CrossClusterAsyncQueryStopIT testStopQuery elastic#124977 Mute org.elasticsearch.xpack.esql.action.CrossClusterAsyncQueryStopIT testStopQueryLocal elastic#121672 Mention zero-window state in networking docs (elastic#124967) Remove remoteAddress field from TransportResponse (elastic#120016) Include failures in partial response (elastic#124929) Prevent work starvation bug if using scaling EsThreadPoolExecutor with core pool size = 0 (elastic#124732) Re-enable analysis stemmer test (elastic#124961) Mute org.elasticsearch.xpack.esql.action.CrossClusterAsyncQueryStopIT testStopQueryLocalNoRemotes elastic#124959 ESQL: Catch parsing exception (elastic#124958) ESQL: Improve error message for ( and [ (elastic#124177) Mute org.elasticsearch.xpack.esql.qa.single_node.EsqlSpecIT test {lookup-join.MvJoinKeyFromRow SYNC} elastic#124951 Mute org.elasticsearch.datastreams.lifecycle.DataStreamLifecycleServiceIT testErrorRecordingOnRetention elastic#124950 ... # Conflicts: # server/src/main/java/org/elasticsearch/index/mapper/vectors/DenseVectorFieldMapper.java # server/src/test/java/org/elasticsearch/index/mapper/vectors/DenseVectorFieldTypeTests.java
Clarify that it is expected sometimes to see inter-node connections sending zero-window advertisements as part of the usual TCP backpressure mechanism.
Clarify that it is expected sometimes to see inter-node connections
sending zero-window advertisements as part of the usual TCP backpressure
mechanism.